Skip to content

Conversation

@lonless9
Copy link
Contributor

Which issue does this PR close?

Rationale for this change

ListFilesEntry is part of the public ListFilesCache trait signature, but it was defined inside the private list_files_cache module and was not re-exported from cache/mod.rs. As a result, downstream crates could not name the return type of ListFilesCache::list_entries, making the public trait effectively unusable.

What changes are included in this PR?

Re-export ListFilesEntry from datafusion_execution::cache

Are these changes tested?

Existing tests.

Are there any user-facing changes?

Fix the broken public API.

@github-actions github-actions bot added the execution Related to the execution crate label Jan 14, 2026
alamb pushed a commit that referenced this pull request Jan 15, 2026
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes #123` indicates that this PR will close issue #123.
-->

- part of #19784.

## Rationale for this change

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

This is a follow-up of #19573

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

Backport 
- #19804

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

Existing tests

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
no
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
@alamb alamb added this pull request to the merge queue Jan 15, 2026
@alamb
Copy link
Contributor

alamb commented Jan 15, 2026

Thank you @lonless9

Merged via the queue into apache:main with commit c173de1 Jan 15, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

execution Related to the execution crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants